Skip to content

Conversation

mroeschke
Copy link
Member

@mroeschke mroeschke commented Mar 11, 2024

I don't think we should necessarily limit this to just to nightly build of these libraries

@mroeschke mroeschke added Testing pandas testing functions or related to the test suite CI Continuous Integration labels Mar 11, 2024
@mroeschke mroeschke changed the title CI: Fail tests on all FutureWarning/DeprecationWarning CI: Fail tests on all builds for FutureWarning/DeprecationWarning from numpy or pyarrow Mar 11, 2024
@lithomas1 lithomas1 added this to the 2.2.2 milestone Mar 12, 2024
Copy link
Member

@datapythonista datapythonista left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, but seems like the minimum versions build is an issue. Seems like we need to keep the test_args to ignore the warnings in that build, or do you have a better idea?

- name: "Pypy"
env_file: actions-pypy-39.yaml
pattern: "not slow and not network and not single_cpu"
test_args: "--max-worker-restart 0"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this related, or is it just not needed and we can remove the whole test_args thing?

@mroeschke
Copy link
Member Author

I think this may be a a little too cumbersome to do as we test downstream libraries and introduce our own deprecations that get reflected in those test so going to close for now

@mroeschke mroeschke closed this Apr 1, 2024
@mroeschke mroeschke deleted the ci/error/futurewarning branch April 1, 2024 18:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CI Continuous Integration Testing pandas testing functions or related to the test suite

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants